Expose structured module load failures#1733
Open
aleksandr-voitenko wants to merge 2 commits into
Open
Conversation
summeroff
approved these changes
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a JS-visible API for structured OBS module load failures.
Motivation and Context
OBS now records structured module load failures with a module name, stable error code, and message. Desktop needs this structured data to show targeted notifications, especially for NDI runtime failures, without parsing logs or relying on the legacy flat failed-module list.
This is part of a coordinated
obs-studio+obs-studio-node+desktopchange, so the new structured failure contract is treated as available.See also:
streamlabs/obs-studio#741
How Has This Been Tested?
Manually, Windows only.
Types of changes